Optimizing A Compiled Access Control Table In A Content Management System

ABSTRACT

A method, computer program product, and system for improving the operation and management of a content management system, by managing data security and incremental refreshes of a compiled access control table. A user may be authorized to access an entity such as a data item by reference to a single table that compiles ACL information from a plurality of tables, without repetitive access to several system tables.

BACKGROUND

1. Technical Field

The present invention relates generally to data security in a content management system, and more particularly to the use and refresh of a compiled access control table.

2. Discussion of Related Art

In a content management system, access to data objects, such as files, folders, databases, and other data elements may be controlled through the use of privilege sets, users and user groups, and access control lists. Users are individuals who are identified as authorized to log on to the system, and user groups are groups of users with common access needs. Each user is assigned a user ID, password, and privilege set. A privilege set identifies the functions that a user can perform, such as creating folders or adding objects to a workbasket.

When a user is logged onto the content management system and makes a request of the system, the system checks the user's privilege set to ensure that the user is allowed to perform the requested function. An access control list (ACL) protects access to the objects (also referred to as items) in the system. An access control list is assigned to each index class, workbasket, and workflow object when it is created. When a logged on user attempts to access an object, the system first checks the user's privilege set to ensure that the user is allowed to perform the requested function, and then checks the access control list for that object to ensure that the user is allowed to perform the requested function on that object. Thus, an access control list may be used to remove otherwise privileged functions—that is, functions which a user is authorized to perform by his privilege set may be denied with respect to a particular object. The result is, that to resolve authorization for a user operating on an item, several system tables must be accessed repetitively. The runtime overhead of such procedural process is a major performance concern.

BRIEF SUMMARY

Accordingly, embodiments of the present invention include a method, computer program product and a system for authorizing access to an entity in a content management system by a user by reference to a single table which compiles access control information from a plurality of tables, comprising binding an entity stored in a content management system to an access control (AC) list table, wherein the AC list table comprises a plurality of access control lists, for each of a plurality of individual users of the content management system, specifying a membership in zero, one or more user groups, specifying a set of group privileges for each user group, specifying a set of user privileges for each individual user that is a member of zero user groups, intersecting the AC list table, the sets of group privileges, and the sets of user privileges in a computer-generated access control list (ACL) table stored in a memory, the columns of the computer-generated ACL table comprising user kind, user identifier, ACL code, and a privilege set comprising a privilege set code and a privilege definition code, and the rows of the computer-generated ACL table corresponding to either a user group, or an individual user that is a member of zero user groups, and incrementally refreshing the computer-generated ACL table responsive to run time modification of the access control list, the sets of group privileges, or the set of user privileges, the incrementally refreshing including, responsive to modification of the privilege set, accessing during on-line execution to affect only rows of the computer-generated ACL table having a corresponding privilege set code.

The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description thereof, particularly when taken in conjunction with the accompanying drawings wherein like reference numerals in the various figures are utilized to designate like components.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary content management system according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating various database tables for use in an exemplary content management system according to an embodiment of the present invention.

FIG. 3 illustrates a system control table 80 according to an embodiment of the present invention.

FIG. 4 illustrates a user table 110 according to an embodiment of the present invention.

FIG. 5 illustrates a user group table 120 according to an embodiment of the present invention.

FIG. 6 illustrates an access codes table 130 according to an embodiment of the present invention.

FIG. 7 illustrates an access control list table 50 according to an embodiment of the present invention.

FIG. 8 illustrates a privileges definitions table 60 according to an embodiment of the present invention.

FIG. 9 illustrates a privilege sets table 70 according to an embodiment of the present invention.

FIG. 10 illustrates a privilege sets code table 140 according to an embodiment of the present invention.

FIG. 11 illustrates a compiled ACL table 150 according to an embodiment of the present invention.

FIGS. 12A and 12B are flowcharts depicting an exemplary process of authorizing user access to store an entity according to an embodiment of the present invention.

FIGS. 13A and 13B are flowcharts depicting an exemplary process of authorizing user access to query/retrieve a stored entity according to an embodiment of the present invention.

FIGS. 14A through 14D are flowcharts depicting an exemplary process of refreshing a compiled ACL table 150 according to an embodiment of the present invention

FIG. 15 is a flowchart depicting an exemplary process of building a compiled ACL table 150 according to an embodiment of the present invention.

DETAILED DESCRIPTION

The present embodiments improve the operation and management of a content management system, by managing data security and incremental refreshes of a compiled access control table. The present embodiments provide that a user may be authorized to access a data item or other data entity by reference to a single table that compiles ACL information from a plurality of tables, without repetitive access to several system tables. The present embodiments also maintain and optimize the currency of a compiled ACL table.

Referring now to the Figures, an exemplary content management environment 100 according to embodiments of the present invention is illustrated in FIG. 1. The exemplary environment 100 comprises user clients 5, which are connected through network 12 to a server 10. Although the system depicted is a client-server system, it is understood that the content management system is not so limited, and can be implemented as a virtual desktop system, in a cloud, data center, distributed network, storage area network (SAN), or in any other suitable system, for example in a system designed for the provision of Software-as-a-Service (SaaS), such as a cloud data center or hosted web service.

Network 12 represents any hardware and/or software configured to communicate information via any suitable communications media (e.g., WAN, LAN, Internet, Intranet, wired, wireless, etc.), and may include routers, hubs, switches, gateways, or any other suitable components in any suitable form or arrangement. The various components of the content management environment 100 may include any conventional or other communications devices to communicate over the networks via any conventional or other protocols, and may utilize any type of connection (e.g., wired, wireless, etc.) for access to the network.

The server 10 comprises a content manager system 20, a database server 22, user applications 24 and exits 26. Content manager (CM) system 20 includes content manager database 30 and stored procedures 32, which procedures 32, among other things, define the methods and tasks executed by CM system 20 with respect to the tables of database 30. System database 30 includes a data storage area 40 storing content manager controlled entities such as user data items 42, collections or libraries (not shown) of user data items, and a table storage area 44 storing various tables such as access control lists 50, a privileges table 60, a privileges set table 70, and several other tables including those shown in FIG. 2.

Data storage area 40 and table storage area 44 may be implemented by any conventional or other memory or storage device, and may be volatile (e.g., RAM, cache, flash, etc.), or non-volatile (e.g., ROM, hard-disk, optical storage, etc.), and include any suitable storage capacity. The data storage area 40 and table storage area 44 may be, for example, one or more databases implemented on a solid state drive or in a RAM cloud.

User clients 5, server 10, CM system 20, database server 22, and content manager database 30, may each be implemented in the form of a processing system, or may be in the form of software. They can each be implemented by any quantity of conventional or other computer systems or devices, such as a computing blade or blade server, thin client, computer terminal or workstation, personal computer (e.g., IBM-compatible PC, Apple Mac, tablet, laptop, netbook, etc.), cellular phone or personal data assistant (e.g., Palm Pre, Droid, iPhone, etc.), or any other suitable device. A processing system may include any commercially available operating system (e.g., AIX, Android, Linux, OSX, Sun Solaris, Unix, Windows, etc.) and any commercially available or custom software (e.g., browser software, communications software, word processing software, etc.). These systems may include processors, memories, internal or external communications devices (e.g., modem, network card, etc.), displays, and input devices (e.g., physical keyboard, touch screen, mouse, microphone for voice recognition, etc.). If embodied in software (e.g., as a virtual image), they may be available on a recordable medium (e.g., magnetic, optical, floppy, DVD, CD, other non-transitory medium, etc.) or in the form of a carrier wave or signal for downloading from a source via a communication medium (e.g., bulletin board, network, LAN, WAN, Intranet, Internet, mobile wireless, etc.).

CM system 20, and the content management environment 100 as a whole, may include additional servers, clients, and other devices not shown, and individual components of the system may occur either singly or in multiples, for example, there may be more than one server 10 in the system, or for example, the functionality of various components may be combined into a single device or split among multiple devices. The server 10 may also be a node, for example a node in a computing cluster, which is connected to other nodes by suitable means, for example via a network. It is understood that any of the various components of the environment 100 may be local to one another, or may be remote from and in communication with one or more other components via any suitable means, for example a network such as a WAN, a LAN, Internet, Intranet, mobile wireless, etc.

Referring to FIG. 2, access to entities (e.g., data items 42) is managed through the use of several relational database tables, including in this preferred embodiment of the invention system control table 80, controlled entities table 90, users table 110, user groups table 120, access codes table 130, access control list table 50, privilege definitions table 60, privilege sets table 70, privilege sets code table 140, and compiled ACL table 150. These tables are stored in table storage area 44 of the CM database 30, and are further described with reference to FIGS. 3 through 11.

Referring to FIG. 3, system control table 80 stores system configuration parameters for CM library server 20. Columns of table 80 include database name 81, ACL binding level 82, library ACL code 83, public access enabled flag 84, and allow trusted logon 85. Database name 81, an installation parameter, is the name of the database (library) server 22. ACL binding level 82 is the access control level used to control access to a CM controlled entity and having, as valid values, 0 at item type level (default), 1 at item level, 2 at mixed item and item type level, and 3 at entire library level. Therefore, depending on how the ACL binding level is set, the access may be controlled at a higher level (e.g., the entity is a library) or a lower and more granular level (e.g., the entity is an item). Library ACL code 83 contains the ACL to be associated with all CM item types and items 42 if the parameter ACL binding level 82 is configured at library level. Public access enabled flag 84 indicates whether the capability of opening a bound entity to public is enabled. When this column 84 is updated, system 20 rebuilds compiled ACL tables 150 and recreates all database table 30 views. Allow trusted logon 85 indicates whether users are permitted to use a trusted logon process to access the database.

Referring to FIG. 4, users table 110 maintains a catalog of individual users and user groups. Individual users can belong to none or any number of groups. Users must be assigned a number of privileges, stored in privilege set code table 130. Defining new CM users does not guarantee their existence in the database management system (DBMS) and the operating system. The system administrator ensures the usefulness of the CM users she creates. A group is a number of zero or more users, usually with the same job description, and assigned the same privilege set. A group cannot belong to other groups. A group does not hold default privileges for its members, nor do they relate to database management system (DBMS) or operating system groups. Defining groups minimizes the effort required to administer access control lists.

In the exemplary user table 110 depicted in FIG. 4, there is an entry or row 111 for each user, and columns including user ID 112, user number 113, user kind 114, user privilege set code 115, grant privilege set code 116, default ACL code 117, password 118, and user name 119. User ID 112 is the ID of the individual user or group. For an individual user, user ID 112 should match her DBMS user ID. The CM system 20 uses this value for user authentication and access control. For a group, user ID 112 contains the group name. User number (UNUM) 113 is a number assigned to each user (individual or group). User kind 114 indicates whether this entry 111 represents an individual user or a group. User privilege set code 115 denotes the user privileges for this user entry 111. The privilege set must be defined first, and this value is not valid for groups. It is set to 1 by CM system 20 for groups. User privilege set code 115 may be updated. Grant privilege set code 116 is the code assigned to new users by a user who is authorized to create users but not grant privileges to the new users. This value 116 is not valid for groups, and it can be updated. A system administrator GUI for creating a user must have an entry field for that user's grant privilege set code 115. Default ACL code 117 is used to associate with data items 42 when the access control is configured at item level if the user does not provide an ACL code when she creates data items 42. Password 118 is the encrypted user password, and user name 119 is the full name of this user or group.

Referring to FIG. 5, users group table 120 maintains associations of individual users with groups. An individual user can belong to none or any number of groups, but a group cannot belong to other groups. When an individual user is associated with a group, the user is said to be a member of that group. The exemplary user group table 120 depicted in FIG. 5 has an entry or row 121 for each individual user's membership in a particular group, and columns for individual user ID 122, individual user number (UNUM) 123, group user ID 124, and group user number (UNUM) 125. For example, the first row 121 in the table indicates that user “J_DOE” having individual UNUM “1000” is a member of group “ADMIN” having group UNUM “2”, and the fourth and fifth rows 121 in the table indicate that user “J_TAYLOR” having individual UNUM “1004” is a member of the “R&D” and “PROJX” groups having group UNUMs “1005” and “1006”, respectively. The association of individual users with groups simplifies access control management, because when access control specifications are defined, a group can be granted a number of privileges that apply to all group members, instead of an administrator having to separately assign the same privileges to each individual user. Each user and group appearing in the user group table 120 must be defined in users table 110 before an association in user group table 120 can be made between the individual user ID 122 and the group ID 124. Rows in this table can only be deleted, not updated.

Referring to FIG. 6, access codes table 130 maintains the access control list codes (identifiers) 132. The exemplary access codes table 130 depicted in FIG. 6 has an entry or row 131 for each access control list, and a column for a unique ACL code (or identifier) 132 that is generated by CM system 20 and cannot be updated. The list specifications are stored in the access control list table 50. ACL name 133 and ACL description 134 are defined in a separate keywords table (not shown). For purposes of illustration only, FIG. 6 depicts a list of pre-configured ACL codes 132.

Referring to FIG. 7, access control list table 50 (also called the ACL Table or AC Lists Table) maintains specifications for one or more access control lists, which are used by the access control algorithm to determine a user's access rights for a data item 42 or other entity. An access control list (ACL) may contain more than one access control (ACL) rule 51, and comprises all rows 51 having the same ACL code 132. Each control 51 is composed of two elements: who (user ID 112, user kind 114) can perform what (privilege set code 72). Each CM data entity (e.g., an item 42) must be bound to a control list in table 50. The control specifications 51 then will be enforced when entities are accessed. For purposes of illustration only, FIG. 7 depicts a list of pre-configured ACLs.

The exemplary ACL table 50 depicted in FIG. 7 has an entry or row 51 for each access control (ACL) rule, and columns for user kind 114, user ID 112, ACL code 132, and privilege set code 72. User ID 112 contains the ID for an individual user or group, and user kind 114 interprets the User ID column as public, group, or individual. If user kind 114 is public, the value in user ID column 112 is ignored. The corresponding types of ACL rules, for illustration purposes, can be given the names ACL rule 51 for user (user kind 114=user), ACL rule 51 for group (user kind 114=group), and ACL rule 51 for public (user kind 114=public), respectively. By specifying public, the ACL rule for public authorizes all the users to perform operations specified in the ACL code 132 on the bound entity, provided the users pass their user privileges check on ACL table 50. The ACL privileges on the bound entity to public (user kind 114=public) can be configured in system level. The configuration parameter is named public access enabled (defined in system control table 80 column 84). The ACL code 132 is the identifier of an individual access control list. Privilege set code 72 is the privilege set identifier, which indicates the operations allowed for the bound entity (e.g., data item 42).

Referring to FIG. 8, privileges definitions table 60 maintains an unlimited number of CM privilege definitions 61, including system-defined system administration privileges 62, system-defined data access privileges 63, and user-defined privileges 64. System defined privileges 62, 63 cannot be modified. Each privilege 61 has a system generated unique privilege definition code 65 as a primary key. Codes 0 to 999 are reserved to store system-defined privileges 62, 63, and codes 1000 and up are open for user defined privileges 64. When defining or updating privilege sets, this privilege definitions table 60 can be first queried to list all defined privileges 61, 62, 63, 64. Applications 24 can also query the privilege definitions table 60 at runtime to get the definitions of the connected user's privileges and customize the application menu selections specifically suitable for that user (at client workstation 5). Privilege name and description are defined in a keywords table (not shown). For purposes of illustration only, FIG. 8 depicts a list of privilege definitions 61 and their corresponding privilege definition codes 65, privilege definition names 66 and privilege definition descriptions 67.

Referring to FIG. 9, privilege sets table 70 maintains associations of individual privileges into privilege sets. Rows 71 with the same privilege set code 72 form a privilege set 141. Rows 71 in the privilege set table 70 can only be deleted, not updated. Columns in privilege sets table 70 include privilege set code 72, which identifies a particular privilege set, and privilege definition code 65. Privilege set name 73 and privilege definition name 66 description are defined in a keywords table (not shown). For purposes of illustration only, FIG. 9 depicts a list of privilege sets and their corresponding privilege set codes 72, privilege set names 73, privilege definition codes 65, and privilege definition names 66.

Referring to FIG. 10, privilege sets code table 140 maintains privilege set definitions. A privilege set 141 is uniquely identified by a system generated privilege set code 72, and comprises an unlimited number of privileges. Its set member associations are stored in privilege sets table 70. Privilege set name 73 and privilege set description 142 are defined in a keywords table (not shown). For purposes of illustration only, FIG. 10 depicts a list of pre-configured privilege sets and their corresponding privilege set codes 72, privilege set names 73, and privilege set descriptions 142.

Referring to FIG. 11, compiled ACL table 150 contains the compiled access control information. Columns in table 150 include user number (UNUM) 113, user kind 114, ACL code 132, privilege set code 72, privilege bits 152, group flag 153, and read privilege flag 154. For each row 151 in compiled ACL table 150, the privilege bits 152 column contains a privilege definition code 65 for each privilege in a particular set for access to a bound entity (e.g., data item 42). ACL code 132 is the access control list code, and the privilege definition codes 65 indicate the operations allowed for the bound entity. Privilege set code 72 is the privilege set code that the resolved privileges are derived from. This is a maintenance field, designed for incremental refresh on this table. For example, when a privilege set 141 is modified, rows 151 with the corresponding privilege set code 72 are affected, while other rows 151 are not. UNUM 113 contains the user number of an authorized user or group, and group flag 153 is set if the entry 151 is derived from an ACL rule for group. This column 153 provides a maintenance field, designed for incremental refresh. It contains null if the ACL rule user kind 114 is not for group. User kind 114 indicates which ACL rule type this row 151 is derived from: public, group or individual user. Read privilege flag 154 indicates whether or not the particular ACL code 132 and privilege set code 72 are associated with a read privilege or not.

Compiled ACL table 150 contains resolved access control information, meaning that each row in the table represents an authorized privilege (privilege bits 152—intersected by user privileges 72 and ACL privileges 132) for a user (or group) that is defined in an ACL rule 50. Thus, privilege definition code 65 is determined if both user privilege (i.e, the general privilege 115) and the ACL privileges 51 show that this user is involved (authorized). In this manner, compiled ACL table 150 is built, as is further described with reference to FIG. 14.

As discussed previously, a CM controlled entity (e.g., data item 42) is bound to an access control list (ACL), which is a group of specific ACL rules 51 having the same ACL code 132. When associated with CM controlled entities, ACL rules 51 define the authorization of the bound entities and do not circumvent user privileges. The access controls are enforced in addition to the user privileges check. Within the same access control list, a user may be specified in more than one type of rule. The precedence of the three types, from highest to lowest, is ACL rule for public (user kind 114=public), ACL rule for user (user kind 114=user), and then ACL rule for group (user kind 114=group). When applying ACL checks, if any higher-precedence rule type passes, the authorization is resolved and the process stops, but if a rule fails, the checking process will continue onto the lower-precedence rule types. When a user is specified in more than one ACL rule of a particular type (e.g., group), the user is authorized by the union of all those rules.

When accessing an entity such as data item 42, this table 150 is joined on the entity's ACL code 132, constrained by the runtime user's number (UNUM) 113 and the desired privilege bits 152. If such a row exists in compiled ACL table 150, the operation on that entity is allowed. Otherwise, it is denied. That is, at runtime, compiled ACL table 150 will be joined by the ACL (i.e., ACL code 132) associated with the specific entity that is filtered out by (i.e, constrained or identified by) user number 113 and the desired privileges 65 in privilege bits column 152. In this manner, content manager 20 performs an ACL code 132 lookup in the compiled ACL table 150 with a given user number 113 and a desired privilege 65.

Table 1 is a pseudo-code representation of how an access lookup may be performed by the CM 20 to check if user 1010 has privileges to store a new entity using ACL 1001, which can stand alone or as a part of the process 300 a described with reference to FIGS. 12A and 12B. Table 2 is a pseudo-code representation of how an access lookup may be performed by the CM 20 to check if user 1010 has privileges to query/retrieve an already stored entity using ACL 1001, which can stand alone or as a part of the process 300 b described with reference to FIGS. 13A and 13B.

TABLE 1 Access Control Lookup (Update/Delete/Create Item) SELECT PRIVS FROM ICMSTCOMPILEDACL ICMC WHERE ACL = <input ACLCode> AND   (UNUM = <InputUserNUM> AND   (EXISTS (SELECT 1     FROM ICMSTUSERGROUPS G     WHERE G.UNUM = <InputUserNUM AND      ICMC.UNUM = G.GNUM) AND      NOT EXISTS (SELECT 1       FROM ICMSTCOMPILEDACL C       WHERE C.UNUM = <InputUserNUM> AND        C.ACL = ICMC.ACL))) UNION SELECT PRIVS   FROM ICMSTCOMPILEDACL   WHERE ACL = <InputACLCode> AND    UNUM = 1 // PUBLIC

TABLE 2 Access Control Lookup (Query/Retrieve Item) SELECT ... FROM ... WHERE ... EXISTS (SELECT 1 FROM ICMSTCOMPILEDACL         WHERE ACLCODE = 1001             and C.RPRIV = ‘1’             and C.USERID = 1010) OR EXISTS (SELECT 1 FROM ICMSTCOMPILEDACL C, ICMSTUSERGROUP UG     WHERE C.ACLCODE=1001     and C.RPRIV=‘1’     and UG.UNUM = C.UNUM     and UG.UNUM = 1010)

The benefits of the present embodiments of the compiled ACL table include enhanced performance because a user may be authorized to access a data item or other data entity by reference to this single table 150 that compiles ACL information from a plurality of tables, without repetitive access to several system tables. Further, the use of a single row for a group of users as opposed to a row for each individual user reduces the size of the table significantly, allows database inserts/deletes to be faster, and reduces the size of index trees and data pages for the compiled ACL table 150. Thus, the present embodiments maximize performance of administration operations involving groups such as creating new ACLs with ACL rules for groups, adding or removing users from groups, or removing ACL rules for groups, because each of these operations affects at most a single row of the compiled ACL table 150 (and in the case of changing user membership in groups, will not affect any rows). Particularly in the case of large database systems with hundreds or thousands of users, the ability to change at most a single row instead of hundreds or thousands of rows each time an ACL rule is changed for a particular group is a significant performance enhancement.

Referring now to FIGS. 12 and 13, reference numerals 300 a, 300 b generally designate flowcharts depicting a process of authorizing user access to store (FIGS. 12A and 12B) or query/retrieve a stored entity (FIGS. 13A and 13B), which may be carried out by the content management system 20 previously described. The processes differ slightly in steps 304, 308 and after step 330, but otherwise are the same.

At step 302 in FIGS. 12A and 13A, the process 300 begins, and at step 304 the CM system 20 receives a user request for access to a stored data entity. In process 300 a, step 304 a is the receipt of a request to store a new data entity, and in process 300 b, step 304 b is the receipt of a request to access an existing data entity already stored in the system. In step 306, the system determines the ACL code 132 of the bound ACL, that is, the ACL list that is bound to the stored data entity, and in step 308 the system searches the compiled ACL table 150 for a set of one or more entries 151 having the ACL code 132 (steps 308 a and 308 b) and having the read flag set, i.e., the read privilege is yes (step 308 b). In step 310, the system determines if public access to the stored data entity is enabled, for example by searching in the system control table 80 for the value of public access enabled flag 84. If the flag is set, meaning that public access is allowed, then the system proceeds to step 312. If the determination in step 310 is that public access is not enabled, i.e., the public access enabled flag 84 is off, then all the ACL rules for public are ignored during the access control process and the system proceeds to step 320.

In step 312, the system determines if any of the entries 151 located in step 308 are public entries, and if yes, proceeds to step 314 and determines if at least one of these public entries permits the requested access to the stored entity. If the determination in step 314 is yes, then the system in step 316 grants the user request and allows the user to access the stored entity, and exits process 300 in step 318. If the determination in step 314 is no, then the system proceeds to step 320. In step 320, the system determines if any of the entries 151 located in step 308 are individual entries, and if yes, proceeds to step 322 and determines if at least one of these entries permits the requested access to the stored entity. If the determination in step 322 is yes, then the system proceeds to step 316 as previously described, but if the determination in step 322 is no, then the system proceeds to step 324 and denies the user request, and in optional step 326 may transmit a notification message to the user. If the determination in step 320 is no, then the system proceeds to step 328.

In step 328 in FIGS. 12B and 13B, the system determines if any of the entries 151 located in step 308 are group entries, and if no, proceeds to step 318 and exits process 300. If the determination in step 328 is yes, then the system proceeds to step 330 and determines for each group entry in the found set, whether the user is a member. In process 300 a (FIG. 12B), if the user is a member, then the system proceeds to step 322 as previously described, but if the user is not a member, then the system proceeds to step 332 and removes that group or groups from the set, and then proceeds to step 322 as previously described. In process 300 b (FIG. 13B), if the user is a member, then the system proceeds to step 322 as previously described, but if the user is not a member, then the system proceeds to step 316 as previously described.

Referring now to FIGS. 14A through 14D, reference numeral 400 generally designates a flowchart depicting a an exemplary process of refreshing a compiled ACL table 150, which may be carried out by the content management system 20 previously described. As discussed previously, compiled ACL table 150 contains the compiled results of access control specifications and must be refreshed when there are changes to the access control system. Ideally, the refresh should occur spontaneously and transparently to the users. As such refresh may be time-costly, content manager system 20 provides both the on-line and off-line refresh mechanisms. There are two approaches for refreshing this table 150: total refresh and incremental refresh. Process 400 describes both types of refresh.

At step 402 in FIG. 14A the process 400 begins, and at step 404 the CM system determines if the compiled ACL table exists already. If not, then the system proceeds to step 406 and builds the compiled ACL table and then exits the process 400 at step 408, but if yes, the system proceeds to step 410. At step 410, the CM system 20 determines if a change has been made in the access control system, e.g., if access control specifications or a configuration that affects the specifications have been changed. If no change was made, the system proceeds to step 408 and exits process 400.

If a change was made, then the CM system proceeds to step 412 and determines if the access control system is offline. If the access control system is offline, then the CM system proceeds to step 414 and performs a total refresh of the compiled ACL table and then exits the process 400 at step 408. If the access control system is online, then the CM system proceeds to step 416 and beyond to incrementally refresh the compiled ACL table.

A total refresh (or build) is desired for initial table population, migration and maintenance. It is straightforward in implementation, but time-consuming when executed. It is suitable for off-line execution. Table 2 is a pseudo-code representation of the access control algorithm for content manager controlled entities, and is initially executed during total refresh and building (steps 410 and 414). An exemplary process 500 for carrying out a build (or total refresh) of the compiled ACL table 150 is also depicted in FIG. 15. It is understood that any suitable process may be used to carry out the total refresh or build of steps 410 and 414, including but not limited to the process in Table 3 or the process 500.

TABLE 3 Access Control Algorithm for CM Controlled Entities   get current user 112 privileges 72   if user privileges 72 allow the operation with super access capability     return granted -- bypass ACL table 50 check   if user privileges 72 do not allow the operation return denied   now, already authorized by the user privileges get the Item's ACL   code 132   try ACL rule 132 for public (user kind 114 = public)   first   if configuration parameter PubAccessEnabled is true     for each ACL Rule in table 50 for public       if ACL privileges 132 allow the operation return granted   continue trying other types of rules   if exists an ACL rule in table 50 for user for this user 115   if ACL privileges 132 allow the operation return granted   else   return denied -- do not try any ACL Rule in table 50   for group (user kind 114 = group)   else for each ACL rule in table 50 for group that contains the   user 112   if ACL privileges 132 allow the operation return granted return denied -- either denied or user 112 is not qualified for any rule in table 50

This total refresh/build process is time consuming, and if it were it the only way to populate compiled ACL table 150, then the CM system would require that the compiled ACL table 150 be rebuilt whenever an update occurs in the relevant system tables, which include in this exemplary embodiment, system tables 50, 60, 70, 110, 120, 130, and 140. Instead, the present embodiments provide for an incremental refresh, which shortens the process time, but complicates the implementation. Because accounting for the access control specification changes for an off-line incremental refresh is a non-trivial task, this approach is generally only applied to on-line execution.

After the CM system completes the build (in step 406) or total refresh (in step 414) of the compiled ACL table, the system then exits the process 400 at step 408.

In step 416, the CM system begins the incremental refresh process. In step 416 the CM system determines if a new ACL rule 51 having ACL code 132 has been added into ACL table 50, and if yes then in step 418 the system adds a new entry or entries (rows 151) to compiled ACL table 150 for the users having user ID 112 in the new ACL rule 51, and then exits the process 400 at step 408. If no new ACL rule was added, then the system proceeds to step 420.

In step 420, the CM system determines if an existing ACL rule 51 in ACL table 50 has been changed or updated, and if yes, then in step 422 the system deletes each corresponding entry (row 151) in compiled ACL table 150, and replaces it with a new entry (row 151) with the changed information, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in table 150 using the ACL code 132 and user ID 112 specified in the deleted rule 51. If no update was made to an existing ACL rule, then the system proceeds to step 424.

Referring now to FIG. 14B, in step 424 the CM system determines if an existing ACL rule 51 was deleted from the ACL table 50, and if yes the system in step 426 deletes each corresponding entry in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in table 150 using the ACL code 132 and user ID 112 specified in the deleted rule 51. If no deletion was made, then the system proceeds to step 428.

In step 428, the CM system determines if a new access control list 131 having an ACL code 132 was added to access codes table 130, and if yes, then in step 430 the system adds a new entry or entries (rows 151) to compiled ACL table 150 for each affected user, and then exits the process 400 at step 408. If no access control list was added, then the system proceeds to step 432. In step 432, the CM system determines if an existing access control list 131 having an ACL code 132 was deleted from access codes table 130, and if yes, then in step 434 the system deletes each corresponding entry in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in table 150 using the deleted ACL code 132. If no deletion was made, then the system proceeds to step 436.

In step 436, the CM system determines if an individual user having user ID 122 was added to a group having group user ID 124 in user group table 120. If yes, the CM system exits the process 400 at step 408, because no change is needed to the compiled ACL table 150. If no, the system proceeds to step 438. In step 438, the CM system determines if an individual user having user ID 122 was removed from a group having group user ID 124 in user group table 120. If yes, the CM system exits the process 400 at step 408, because no change is needed to the compiled ACL table 150. If no, the system proceeds to step 440.

Referring now to FIG. 14C, at step 440 the CM system determines if a new individual user having user ID 112/122 was added to users table 110. If yes, the system in step 442 adds a new entry or entries (rows 151) to compiled ACL table 150 for the new user, if that user is not a group member and has super access capability privileges designated in user privilege set code 115, and then exits the process 400 at step 408. If no, the system proceeds to step 444.

At step 444 the CM system determines if an existing individual user having user ID 112/122 had her general privileges in user privilege set code 115 changed in users table 110. If yes, the system in step 446 deletes each corresponding entry in compiled ACL table 150 (if any exist), and then adds a new entry or entries (rows 151) to the compiled ACL table 150 to replace any deleted entry or entries, before exiting the process 400 at step 408. If no, the system proceeds to step 448. If the individual user 112/122 belongs to a group, then there will be no entries in compiled ACL table 150 to delete and replace.

At step 448 the CM system determines if an existing individual user 112/122 was deleted from the users table 110. If yes, the system in step 450 deletes each corresponding entry in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in compiled ACL table 150 using the user ID 112/122 of the deleted user. If the individual user 112/122 belongs to a group, then there will be no entries in compiled ACL table 150 to delete. If no, the system proceeds to step 452.

At step 452 the CM system determines if an existing group having user ID 112/124 (or a public group) was removed from the system user group table 120. If yes, the system in step 454 deletes each corresponding entry in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in compiled ACL table 150 using the user ID 112/124 of the deleted user group. If no, the system proceeds to step 456.

At step 456 the CM system determines if a new privilege set member 71 having privilege definition code 65 was added to an existing privilege set 72 in privilege sets table 70, and the existing privilege set 72 is used in any individual ACL rules 132. If yes, then in step 458 the system adds the new privilege code 65 to the privilege bit column 152 for each affected row 151 in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in compiled ACL table 150 using privilege set code 72 and privilege definition code 65. If no, the system proceeds to step 460.

Referring now to FIG. 14D, at step 460 the CM system determines if an existing privilege set member 71 having privilege definition code 65 was deleted from an existing privilege set 72 in privilege sets table 70, and the existing privilege set 72 is used in any individual ACL rules 132. If yes, then in step 462 the system deletes each corresponding privilege code 65 from the privilege bit column 152 for each affected row 151 in compiled ACL table 150 and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in compiled ACL table 150 using privilege set code 72 and privilege definition code 65. If no, the system proceeds to step 464.

At step 464, the CM system determines if an existing privilege set 141 having privilege set code 72 was deleted from privilege sets code table 140. If yes, then in step 466 the system deletes each corresponding entry in compiled ACL table 150, and then exits the process 400 at step 408. The system may, for example, search for corresponding entries in compiled ACL table 150 using deleted privilege set code 72. If no, the system proceeds to step 468.

At step 468, the CM system determines if a new privilege 61 having privilege definition code 65 was added to privilege definitions table 60, and was added to an existing privilege set having privilege set code 72 in privilege set table 70. If yes, then in step 470 the system adds a new entry or entries (rows 151) to compiled ACL table 150, and then exits the process 400 at step 408. For example, the exemplary system pre-defined privilege set named “AllPrivSet” includes every privilege, and thus a new entry for the new privilege 61 will be added to the compiled ACL table 150 each time the “AllPrivSet” privilege set appears in compiled ACL table 150. If no, the system proceeds to step 472.

At step 472, the CM system determines if an existing privilege 61 having privilege definition code 65 was deleted from privilege definitions table 60, and was a member of an existing privilege set having privilege set code 72 in privilege set table 70. If yes, then in step 474 the system deletes each corresponding entry in compiled ACL table 150 m and then exits the process 400 at step 408. For example, the exemplary system pre-defined privilege set named “AllPrivSet” includes every privilege, and thus the removal of a privilege 61 necessitates a deletion of the corresponding entry in the compiled ACL table 150 each time the “AllPrivSet” privilege set appears in compiled ACL table 150. If no, the system then exits the process 400 at step 408.

Referring now to FIG. 15, reference numeral 500 generally designates a flowchart depicting a an exemplary process of building (or performing a total refresh of) a compiled ACL table 150, which may be carried out by the content management system 20 previously described. The process 500 is simplified for the sake of illustrative purposes, and is not limited to the steps depicted and described, which focus on several aspects of the build process.

At step 502 in FIG. 15 the process 500 begins, and at step 504 the CM system binds each stored data entity to the desired access control list. In step 506, the system determines if all desired users have been added to users table 110, and if not, in step 508 adds the user or users to the users table 110, and then proceeds to step 510. If the determination in step 506 is yes, then the system proceeds to step 510. In step 510, the system determines if all desired groups have been added to users table 110, and if not, in step 512 adds the group or groups to the users table 110, and in step 514 specifies a set of group privileges for each group in ACL table 50, and then proceeds to step 516. If the determination in step 510 is yes, then the system proceeds to step 516.

In step 516, the system determines if all desired group memberships have been added to user groups table 120. If not, the system in step 518 specifies user membership in desired groups in user groups table 120, for example by adding a row for each individual user's membership in each desired group, and then proceeds to step 520. If the determination in step 516 is yes, then the system proceeds to step 520. In step 520, the system determines, for each user in users table 110, if the user is a member of one or more groups, and if not, in step 522 specifies a set of user privileges for each such user in the ACL table 50, and then proceeds to step 524. If the determination in step 520 is yes, then the system proceeds to step 524.

In step 524, the system builds the compiled ACL table 150 by intersecting the ACL table 50 with the users table 110 (and any other desired table). As described previously with reference to FIG. 11, the columns of the ACL table including user number 113, user kind 114, ACL code 132, a privilege set code 72, privilege bits 152 including one or more privilege definition codes 65, a group flag 153, and a read flag 154. As can be understood from the description of process 500, the rows of the ACL table each correspond to either a user group, or an individual user that is a member of zero groups (because only such individual users have a set of privileges defined in ACL table 50). Thus, if an individual user is a member of one or more groups, there will not be any rows in the ACL table corresponding to such users. Instead, a user who is a group member will have her privileges determined by the group or groups to which she belongs. It is also understood that a set of privileges 72 is represented by a row in the compiled ACL table 150. Thus, if a particular group has a set of group privileges including five different privileges, then there will be five corresponding privilege definition codes 65 in the privilege bit column 152 for that row.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a solid state disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, a phase change memory storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, e.g., an object oriented programming language such as Java, Smalltalk, C++ or the like, or a conventional procedural programming language, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

It is to be understood that the software for the computer systems of the present invention embodiments may be implemented in any desired computer language and could be developed by one of ordinary skill in the computer arts based on the functional descriptions contained in the specification and flow charts illustrated in the drawings. By way of example only, the software may be implemented in the C++, Java, P1/1, Fortran or other programming languages. Further, any references herein of software performing various functions generally refer to computer systems or processors performing those functions under software control.

The computer systems of the present invention embodiments may alternatively be implemented by any type of hardware and/or other processing circuitry. The various functions of the computer systems may be distributed in any manner among any quantity of software modules or units, processing or computer systems and/or circuitry, where the computer or processing systems may be disposed locally or remotely of each other and communicate via any suitable communications medium (e.g., LAN, WAN, Intranet, Internet, hardwire, modem connection, wireless, etc.).

Aspects of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

A processing system suitable for storing and/or executing program code may be implemented by any conventional or other computer or processing systems preferably equipped with a display or monitor, a base (e.g., including the processor, memories and/or internal or external communications devices (e.g., modem, network cards, etc.) and optional input devices (e.g., a keyboard, mouse or other input device)). The system can include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the system to become coupled to other processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, method and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometime be executed in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated. 

1. A computer-implemented method for authorizing access to an entity in a content management system by a user by reference to a single table which compiles access control information from a plurality of tables, comprising: binding an entity stored in a content management system to an access control (AC) list table, wherein the AC list table comprises a plurality of access control lists; for each of a plurality of individual users of the content management system, specifying a membership in zero, one or more user groups; for each user group, specifying a set of group privileges; for each individual user that is a member of zero user groups, specifying a set of user privileges; intersecting the AC list table, the sets of group privileges, and the sets of user privileges in a computer-generated access control list (ACL) table stored in a memory, the columns of the computer-generated ACL table comprising user kind, user identifier, ACL code, and a privilege set comprising a privilege set code and a privilege definition code, and the rows of the computer-generated ACL table corresponding to either a user group, or an individual user that is a member of zero user groups; and incrementally refreshing the computer-generated ACL table responsive to run time modification of the access control list, the sets of group privileges, or the set of user privileges, said incrementally refreshing including, responsive to modification of the privilege set, accessing during on-line execution to affect only rows of the computer-generated ACL table having a corresponding privilege set code.
 2. The computer implemented method of claim 1, further comprising: deriving the computer-generated ACL table from a set of relevant tables stored in the memory; and said incrementally refreshing being selectively executed to update the computer-generated ACL table responsive to run time modification of the relevant tables.
 3. The computer implemented method of claim 2, further comprising: maintaining as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row in the user groups table, making no change to the computer-generated ACL table.
 4. The computer implemented method of claim 2, further comprising: maintaining as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to deletion of a row from the user groups table, making no change to the computer-generated ACL table.
 5. The computer implemented method of claim 2, further comprising: maintaining as one of the set of relevant tables an access codes table, the access codes table comprising ACL code indicia uniquely identifying each access control list in the AC list table; and responsive to insertion of an ACL code indicia into the access codes table that impacts an individual user who has super access capability and that is a member of zero user groups, inserting a corresponding row into the computer-generated ACL table.
 6. The computer implemented method of claim 2, further comprising: maintaining as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintaining as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row to the users table for a new individual user whose corresponding user privilege set indicia includes indicia of super access capability, either adding a row to the user groups table for the new individual user, or adding a corresponding entry to the computer-generated ACL table for the new individual user.
 7. The computer implemented method of claim 2, further comprising: maintaining as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintaining as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to updating of a row in the users table for an individual user whose corresponding user privilege set indicia includes indicia of super access capability, removing and then adding corresponding entries in the computer generated ACL table for the individual user.
 8. A computer program product for authorizing access to an entity in a content management system by a user by reference to a single table which compiles access control information from a plurality of tables, comprising: a computer readable storage device having computer readable program code stored thereon, the computer readable program code comprising computer readable program code configured to: bind an entity stored in a content management system to an access control (AC) list table, wherein the AC list table comprises a plurality of access control lists; for each of a plurality of individual users of the content management system, specify a membership in zero, one or more user groups; for each user group, specify a set of group privileges; for each individual user that is a member of zero user groups, specify a set of user privileges; intersect the AC list table, the sets of group privileges, and the sets of user privileges in a computer-generated access control list (ACL) table stored in a memory, the columns of the computer-generated ACL table comprising user kind, user identifier, ACL code, and a privilege set comprising a privilege set code and a privilege definition code, and the rows of the computer-generated ACL table corresponding to either a user group, or an individual user that is a member of zero user groups; and incrementally refresh the computer-generated ACL table responsive to run time modification of the access control list, the sets of group privileges, or the set of user privileges, said incrementally refresh including, responsive to modification of the privilege set, accessing during on-line execution to affect only rows of the computer-generated ACL table having a corresponding privilege set code.
 9. The computer program product of claim 8, wherein the computer readable program code is further configured to: derive the computer-generated ACL table from a set of relevant tables stored in the memory; and selectively execute the incremental refresh to update the computer-generated ACL table responsive to run time modification of the relevant tables.
 10. The computer program product of claim 9, wherein the computer readable program code is further configured to: maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row in the user groups table, make no change to the computer-generated ACL table.
 11. The computer program product of claim 9, wherein the computer readable program code is further configured to: maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to deletion of a row from the user groups table, make no change to the computer-generated ACL table.
 12. The computer program product of claim 9, wherein the computer readable program code is further configured to: maintain as one of the set of relevant tables an access codes table, the access codes table comprising ACL code indicia uniquely identifying each access control list in the AC list table; and responsive to insertion of an ACL code indicia into the access codes table that impacts an individual user who has super access capability and that is a member of zero user groups, insert a corresponding row into the computer-generated ACL table.
 13. The computer program product of claim 9, wherein the computer readable program code is further configured to: maintain as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row to the users table for a new individual user whose corresponding user privilege set indicia includes indicia of super access capability, either add a row to the user groups table for the new individual user, or add a corresponding entry to the computer-generated ACL table for the new individual user.
 14. The computer program product of claim 9, wherein the computer readable program code is further configured to: maintain as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to updating of a row in the users table for an individual user whose corresponding user privilege set indicia includes indicia of super access capability, remove and then add corresponding entries in the computer generated ACL table for the individual user.
 15. A system for authorizing access to an entity in a content management system by a user by reference to a single table which compiles access control information from a plurality of tables, comprising: a memory having a plurality of entities stored therein; an access control (AC) list table bound to a stored entity, wherein the AC list table comprises a plurality of access control lists; and a processor configured with logic to: for each of a plurality of individual users, specify a membership in zero, one or more user groups; for each user group, specify a set of group privileges; for each individual user that is a member of zero user groups, specify a set of user privileges; intersect the AC list table, the sets of group privileges, and the sets of user privileges in a computer-generated access control list (ACL) table, the columns of the computer-generated ACL table comprising user kind, user identifier, ACL code, and a privilege set comprising a privilege set code and a privilege definition code, and the rows of the computer-generated ACL table corresponding to either a user group, or an individual user that is a member of zero user groups; and incrementally refresh the computer-generated ACL table responsive to run time modification of the access control list, the sets of group privileges, or the set of user privileges, said incrementally refresh including, responsive to modification of the privilege set, accessing during on-line execution to affect only rows of the computer-generated ACL table having a corresponding privilege set code.
 16. The system of claim 15, wherein the processor is further configured with logic to: derive the computer-generated ACL table from a set of relevant tables stored in the memory; and selectively execute the incremental refresh to update the computer-generated ACL table responsive to run time modification of the relevant tables.
 17. The system of claim 16, wherein the processor is further configured with logic to: maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row in the user groups table, make no change to the computer-generated ACL table.
 18. The system of claim 16, wherein the processor is further configured with logic to: maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to deletion of a row from the user groups table, make no change to the computer-generated ACL table.
 19. The system of claim 16, wherein the processor is further configured with logic to: maintain as one of the set of relevant tables an access codes table, the access codes table comprising ACL code indicia uniquely identifying each access control list in the AC list table; and responsive to insertion of an ACL code indicia into the access codes table that impacts an individual user who has super access capability and that is a member of zero user groups, insert a corresponding row into the computer-generated ACL table.
 20. The system of claim 16, wherein the processor is further configured with logic to: maintain as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to insertion of a row to the users table for a new individual user whose corresponding user privilege set indicia includes indicia of super access capability, either add a row to the user groups table for the new individual user, or add a corresponding entry to the computer-generated ACL table for the new individual user.
 21. The system of claim 16, wherein the processor is further configured with logic to: maintain as one of the set of relevant tables a users table, the columns of the users table comprising individual user identification indicia and corresponding user privilege set indicia for at least one individual user; maintain as one of the set of relevant tables a user groups table, the columns of the user groups table comprising group user indicia and individual user identification indicia, and the rows of the user groups table corresponding to an individual user that is a member of at least one user group; and responsive to updating of a row in the users table for an individual user whose corresponding user privilege set indicia includes indicia of super access capability, remove and then add corresponding entries in the computer generated ACL table for the individual user. 